Method and system for managing processing resources

ABSTRACT

The present disclosure improves upon existing systems and methods by providing a tool for managing processing resources. For instance, the presently described tool may be used to time replacement, plan for uplifts, budget for uplifts/decommissioning of hardware, and/or maintain a plurality of servers. This tool may lead to increased satisfaction, uptime, and a reduction of unexpected costs. The system may include initiating collection of variables to compile a prioritized list of servers, executing, a calculation application for determining a prioritized list of servers&#39; end of life targets based on both technical and business parameters based on the entered variables, and prioritizing uplifts of the servers based on the technical and the business parameters.

FIELD

The present disclosure generally relates to resource management. Moreparticularly, the disclosure relates to methods, systems, and computerreadable medium for managing processing resources.

BACKGROUND ART

An organization may use servers to host applications and provide one ormore services. For the organization to operate normally, it is importantto keep the servers in a functional state. At times, a server may stopfunctioning due to various reasons, such as, failure in server hardware,server software, applications and/or services hosted by the server,and/or combination thereof. In some cases, the failure of a server isabrupt and is not foreseen. For example, an unexpected crash of anoperating system of a server may cause an abrupt failure. In othercases, the failures in the server may be more predictable. For example,risk of hardware failure increases as the hardware ages. The abrupt orpredictable failures of the one or more servers may disrupt the normalfunctioning of the organization. Such disruptions are not desirable fromthe organization's perspective. The disruptions may cause loss of data,loss of man hours, and/or loss in revenue, etc. Also, the disruptionsmay cause inconvenience to merchants and/or customers of theorganization. This may lead to loss of confidence of the customersand/or the merchants in the organization.

SUMMARY OF THE DISCLOSURE

The above needs are successfully met via the disclosed system andmethod. Moreover, the present disclosure improves upon existing systemsand methods by providing a tool for managing processing resources. Forinstance, the presently described tool may be used to time replacement,plan for uplifts, budget for uplifts/decommissioning of hardware, and/ormaintain a plurality of servers. This tool may lead to increasedsatisfaction, uptime, and a reduction of unexpected costs.

In accordance with various embodiments, the system comprises accessingvariables, wherein the variables facilitate compiling a prioritized listof servers, executing, a calculation application for determining aprioritized list of servers' end of life targets based on both technicaland business parameters via the entered variables, and prioritizinguplifts of the servers based on the technical and the businessparameters. In some embodiments, a server may be removed from theprioritized list of servers based on an indicator signifying the serveris previously designated to be uplifted. For instance, in the case wherethere is an indication that a business unit is planning on paying forthe uplift (such as out of turn) and/or the uplift was needed due to anunforeseen need.

The variables discussed above may include the install date, theoperating system of an application being processed by each server, aSarbanes-Oxley score designated to an application processed by theserver, and a data security score attributed to an application processedby the server. The business parameters may comprise an applicationcriticality score which may be based on a combination of a SarbanesOxley score and a data security score of the applications processed bythe server. For instance, the Sarbanes Oxley score may be based on aSarbanes Oxley code designated to and associated with each applicationprocessed by the server based on the application's association with theSarbanes Oxley Act of 2002.

The computer based system may budget uplifts in advance based on apriority. The server's end of life target may be based on a matrix.Within this matrix, the operating system platform of the server and/orapplications running on the server may be compared with an applicationcriticality of application processed by the server. The server's end oflife calculated target date may include a designated year for upliftingas calculated from the installation date of the server.

In various embodiments, the technical and the business parameters maycomprise server characteristics, uptime reliability score, flexibility,and a maintenance cost score. In various embodiments, the servercharacteristics comprise a virtual or physical server designation. Invarious embodiments, the uptime reliability score is based on at leastone of the age of the server, the server utilization, the applicationcriticality, the age of manufacturer' hardware model, the hardwarewarranty status, and availability of operating system support.

Also, in various embodiments, the flexibility is based on at least oneof the age of the manufacturer's hardware model and an alignment withcurrent hardware standards of an organization running applications onthe server. In various embodiments, the maintenance cost score is basedon at least one of the alignment with current hardware standards of anorganization running applications on the server, designation of orphanedservers and/or the power consumption of the server. The computer basedsystem may specify servers with a history of faults ahead of/as a higherpriority than older servers on an individual basis.

In various embodiments the data security score is based on an assignedscaled weight of security used by each application running on eachserver. This weight may be calculated and/or assigned during an audit.In various embodiments the data security score is based on at least oneof a public, business confidential, restricted or secret designation ofan application processed by the server. The prioritization may beupdated/re-prioritized based on the start of a new budget term.

Further features and advantages of the present disclosure as well as thestructure and operation of various embodiments are described in detailbelow with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The features and advantages of the present disclosure will become moreapparent from the detailed description set forth below when taken inconjunction with the drawings, in which like reference numbers indicateidentical or functionally similar elements. Additionally, the left-mostdigit of a reference number identifies the drawing in which thereference number first appears.

FIG. 1 is an overview of an example computer-based system for managingprocessing resources, according to various embodiments of the presentdisclosure;

FIG. 2 is a flowchart illustrating one example process for calculatingend of life of a server, according to various embodiments of the presentdisclosure;

FIG. 3 is a flowchart illustrating an example process for prioritizinguplifts for each of the servers to create a priority, according tovarious embodiments of the present disclosure;

FIG. 4 is a process flow illustrating an example process for managingprocessing resources, according to various embodiments of the presentdisclosure; and

FIG. 5 is a block diagram of an exemplary computer system, according tovarious embodiments of the present disclosure.

DETAILED DESCRIPTION

The detailed description of exemplary embodiments herein makes referenceto the accompanying drawings and pictures, which show variousembodiments by way of illustration. While these various embodiments aredescribed in sufficient detail to enable those skilled in the art topractice the disclosure, it should be understood that other embodimentsmay be realized and that logical and mechanical changes may be madewithout departing from the spirit and scope of the disclosure. Thus, thedetailed description herein is presented for purposes of illustrationonly and not of limitation. For example, the steps recited in any of themethod or process descriptions may be executed in any order and are notlimited to the order presented. Moreover, any of the functions or stepsmay be outsourced to or performed by one or more third parties.Furthermore, any reference to singular includes plural embodiments, andany reference to more than one component may include a singularembodiment.

Systems, methods and computer program products are provided. In thedetailed description herein, references to “various embodiments”, “oneembodiment”, “an embodiment”, “an example embodiment”, etc., indicatethat the embodiment described may include a particular feature,structure, or characteristic, but every embodiment may not necessarilyinclude the particular feature, structure, or characteristic. Moreover,such phrases are not necessarily referring to the same embodiment.Further, when a particular feature, structure, or characteristic isdescribed in connection with an embodiment, it is submitted that it iswithin the knowledge of one skilled in the art to affect such feature,structure, or characteristic in connection with other embodimentswhether or not explicitly described. After reading the description, itwill be apparent to one skilled in the relevant art(s) how to implementthe disclosure in alternative embodiments.

In various embodiments, the methods described herein are implementedusing the various particular machines described herein. The methodsdescribed herein may be implemented using the below particular machines,and those hereinafter developed, in any suitable combination, as wouldbe appreciated immediately by one skilled in the art. Further, as isunambiguous from this disclosure, the methods described herein mayresult in various transformations of certain articles.

For the sake of brevity, conventional data networking, applicationdevelopment and other functional aspects of the systems (and componentsof the individual operating components of the systems) may not bedescribed in detail herein. Furthermore, the connecting lines shown inthe various figures contained herein are intended to represent exemplaryfunctional relationships and/or physical couplings between the variouselements. It should be noted that many alternative or additionalfunctional relationships or physical connections may be present in apractical system.

FIG. 1 is an overview of an example system 100 for managing processingresources, in accordance with various embodiments of the presentdisclosure. System 100 determines end of life (EOL) for resources.System 100 also provides data associated with the health of theresources that can be used in planning for replacement of the resource,uplifts of a resource, budget for uplifts/decommissioning of hardware,and/or maintenance of plurality of resources. The resources as describedherein may refer to a plurality of servers of an organization. In anexample implementation, system 100 includes a processing module 102, aserver repository 104 and an application repository 106.

Processing module 102 may access a variable from server repository 104and/or application repository 106. Processing module 102 may compile aprioritized list of servers among the plurality of servers by processingthe variable. The variable may include a server install date, anoperating system of an application being processed by each server of theplurality of servers, a Sarbanes-Oxley score designated to anapplication processed by each server of the plurality of servers, and adata security score attributed to an application processed by eachserver, among others. In an example, the prioritized list of servers mayrefer to servers that may have reached end of a useful service lifeand/or are likely to have hardware and/or software problems in the nearfuture. For instance, the hardware problems may be due to ageing of thecomponents. The software problems may be due to change in standards ofthe software, lack of support from product provider, and/or the like.The prioritized list of servers may have to be uplifted based on apriority, to plan for/avoid any potential impact on applications and/orservices hosted therein. The term ‘uplift’ may refer to replacement,refresh, modification, upgrade or update in hardware and/or software ofthe server, or any combination thereof. The applications may include anyapplication. For example, the applications may include accountingapplications, office applications, platform specific applications,middleware, infrastructure applications, and the like, that supportbusiness operations of the organization. The services may includeapplications that support customers/merchants of the organization suchas, online account services, trading services, and/or the like.

Processing module 102 determines end of life (BOL) targets for theplurality of servers based on a first set of technical and/or businessparameters of the applications running on each server of the pluralityof servers. The first set of technical and business parameters of theapplications are based on the variables. The first set of technicalparameters may include a server install date and an operating system ofan application being processed by each server of the plurality ofservers. The first set of business parameters may include an applicationcriticality score assigned to an application and may be based on acombination of a Sarbanes Oxley score and a data security score of theapplication processed by each server. The server install date asdiscussed herein refers to a date of installation of a server. Theoperating system of an application may refer to the operating system onwhich the application is being processed by a server. The Sarbanes Oxley(SOX) score may refer to a value based on a Sarbanes Oxley codedesignated to each application processed by each server based on theapplication's association with/relevance to the Sarbanes Oxley Act of2002. Processing module 102 may access SOX scores for each of theapplications from application repository 106. The SOX scores may bebased on the application being active, inactive or not being SOXcritical. The data security score may indicate a weight of the securityof an application for the organization and/or customer. The datasecurity score may be based on an assigned scaled weight of securityneeded for each application running on each server of the plurality ofservers. The applications may be designated as one of public, businessconfidential, restricted or secret, based on a scaled weight of thesecurity needed. Each of the applications may be assigned with the datasecurity score based on the designation. For example, applicationshaving secret data, such as, trade secrets, may be assigned with maximumsecurity weight and correspondingly, a maximum data security score maybe assigned. In another example, applications having basic public datamay have security weigh which is less than the applications havingsecret data and correspondingly, the data security score for theapplications having public data would be less compared to the datasecurity score of the secret data.

Processing module 102 may provide a weight to the SOX score and the datasecurity score. Processing module 102 may also obtain the weight fromserver repository 104. For instance, application details may be storedby the Application Repository. These application details may include anindicator provided based on an assessment to designate if theapplication is a SOX critical application or not. The application mayalso be designated with an indicator designating if the application isactive or inactive. For example, according to various embodiments, theremay be 3 distinct status' assigned, 1) Active (SOX critical app), 2)Inactive or 3) Never been SOX critical. A high weightage may be assignedto a SOX critical application (e.g. a score of 100) and a low weightagemay be assigned non critical applications (e.g. a score of 0). Thesescores in combination may then be used to calculate overall SOX score ofthe server.

According to various embodiments, these application details may includean indicator provided based on an assessment to designate the datasecurity of each application. For example, an indication that theapplication contains or processes data that is classified as Public,Confidential, Restricted or Secret in nature. This may be based on astandard, such as transaction account issuer Information SecurityStandard. According to an embodiment, based on the information, a scoremay be assigned to each application. For example, secret may have thehighest score and it would be considered as more critical than anapplication processing data with a Public category designation. Thesescores in combination may then be used to calculate overall datasecurity score of the server.

Stated another way, based on the weights, processing module 102 maydetermine the application criticality score for each applicationprocessed by each server. The application criticality score may indicatethe importance of the application for the organization, the customerand/or the merchant. Based on the application criticality score,processing module 102 may determine the application criticality. Forexample, processing module 102 may determine that an applicationcriticality is high, if the application criticality score is more than apre-defined threshold score. Otherwise, processing module 102 maydetermine that the application criticality is low. Based on theapplication criticality and the operating system of an application beingprocessed by a server, processing module 102 may determine the EOLtargets for each of the plurality of servers using a matrix. The matrixmay include values that correspond to the application criticality andthe operating system platform of the application. Within the matrix,processing module 102 may compare the operating system platform of theapplication processed by the server with the application criticality ofapplication processed by the server. Based on the values in the matrix,processing module 102 determine the EOL targets for each of theplurality of servers. The EOL target for each server may include adesignated year for uplifting the server as calculated from theinstallation date of the server.

Processing module 102 prioritizes uplifts of each of the plurality ofservers to create a priority. The priority indicates list of serversthat may require replacements and/or uplifts in hardware and/or softwareon a priority basis to avoid any impact on the applications and/or theservices. The priority may indicate an order in which servers that mayrequire uplifts. Processing module 102 may prioritize uplifts based on asecond set of technical and business parameters. The second set oftechnical and business parameters may include server characteristics,uptime reliability score, flexibility, a maintenance cost score, and/orthe like. The server characteristics may include a virtual or physicalserver designation. The servers may be implemented as a ‘V parent’, aphysical server, a virtual server, a ‘VSS’, and/or the like. The ‘Vparent’ and the physical server may be designated as a physical server.The virtual server and the VSS may be designated as a virtual server.Processing module 102 may obtain the server characteristics from serverrepository 104. The uptime reliability score may indicate thereliability of the server. Processing module 102 may generate the uptimereliability score based on one or more of the age of each server, eachserver's utilization, an application being processed by each server'scriticality, age of manufacturer' hardware model for each server,hardware warranty status for each server, availability of operatingsystem support for each server, and/or the like. According to variousembodiments, processing module 102 may obtain the uptime reliabilityscore from server repository 104.

The parameter ‘flexibility’ may indicate the age of hardware model ofthe server and ease of alignment of the server with current hardwarestandards. Processing module 102 may calculate the flexibility parameterbased on one or more of the age of the manufacturers hardware modeland/or ease of the server alignment with current hardware standards ofan organization running applications on each server. In another example,processing module 102 may obtain the flexibility parameter from serverrepository 104. The maintenance cost score for a server may indicate thecost of maintaining the server. Processing module 102 may generate themaintenance cost score based on one or more of capability of aligningthe server with current hardware standards of an organization runningapplications on each server, designation of orphaned servers, powerconsumption of each server, etc.

Processing module 102, upon determining EOL targets for each of theplurality of servers and/or creating the priority, may budget theuplifts based on the priority. Processing module 102 may mark one ormore of the plurality of servers for uplift based on the priority.Processing module 102 may determine EOL targets for each server of theorganization and/or create the priority at periodical intervals, forexample, at the start of each budget year, at the beginning of eachquarter, every semester, at other predetermined intervals, etc.Processing module 102 may also perform these tasks in response to arequest, for example, as a part of an audit process within theorganization at any time. The priority may be updated based on thisaudit. With the EOL targets and priority list, resource staff may beequipped with data for budgeting for server uplifts and changes inarchitecture. Processing module 102 may remove a server in the list ofprioritized set of servers based on an indicator signifying the serveris previously designated to be uplifted. For example, one or moreservers that have history of faults may be marked with an indicator foruplifting even before creating the priority. In another example, one ormore servers that may have failed abruptly due to various reasons suchas hardware failure, virus attacks, and/or the like may be marked withan indicator for uplifting. Processing module 102 may obtain theindicator from server repository 104 and/or application repository 106.

In various embodiments, processing module 102 as described herein may bea computer-based system such as, for example, a server, any suitablepersonal computer, a mobile device, a personal data assistant (PDA), anetwork computer, a workstation, a minicomputer, a mainframe or thelike. In various embodiments, processing module 102 may be a componentthat can be implemented in the computer-based systems. Processing module102 may also be an independent component made of hardware, software, orhardware and software that can be implemented in or in conjunction withthe computer-based systems. Those skilled in art can appreciate thatcomputer-based system includes an operating system (e.g. Windows NT,95/98/2000, OS2, UNIX, Linux, Solaris, MacOS, etc.) as well as variousconventional support software and drivers typically associated withserver/computer. Processing module 102 as described herein may bedeployed by the organization and/or or a third-party associated with theorganization.

In various embodiments, processing module 102 may be implemented as aset of computer related instructions. Processing module 102 may beconfigured to execute a set of computer related instructions.

Server repository 104 may include information about the plurality ofservers of the organization. The information may include installationdates of server, the operating systems run by each of the plurality ofservers, the applications run by each of the of the plurality ofservers, the operating system on which the applications are run, theserver characteristics of each of the plurality of servers, age ofservers of each of the plurality of servers, utilization data of each ofthe plurality of servers, application criticality data run by each ofthe plurality of servers, age of manufacturers hardware model for eachof the plurality of servers, hardware warranty data of each of theplurality of servers, data indicating whether manufacturer of theoperating system is providing the support for each of the operatingsystems run on each of the plurality of servers, data indicating howmuch the server hardware is aligned with the current hardware standards,applications being terminated, data associated with orphaned servers,power consumed by each of the plurality of servers, data indicatingwhether the server, operating system and/or applications are marked fordecommission or uplift, and the like.

Application repository 106 may include information about theapplications of the organization, types of the applications, theapplications run on each of the plurality of servers, the applicationsrun on each of the plurality of servers, the applications run on theoperating systems of plurality of servers, Sarbanes-Oxley data for eachof the applications, data security weight for each of the applications,and the like.

Server repository 104 and/or application repository 106 may include dataabout the organization infrastructure related programs. The data relatedto the organization infrastructure related programs may includeinformation about changes in server infrastructure, plans formodification of the organization infrastructure such as, server beingmarked for uplift decommissioning, application rationalization,application decommissioning, and/or application infrastructure upliftfor all the applications on the server. Although, FIG. 1 illustratesserver repository 104 and application repository 106 as separaterepositories, server repository 104 and application repository 106 canbe implemented as one repository or multiple repositories.

Server repository 104, application repository 106 may comprise datewhich may be retrieved by the system to calculate a prioritized list,such as a list of server uplifts. Server repository 104, applicationrepository 106 and/or one or more databases associated with system 100may employ any type of database, such as relational, hierarchical,graphical, object-oriented, and/or other database configurations. Thedatabases may be organized in any suitable manner, for example, as datatables or lookup tables. Each record may be a single file, a series offiles, a linked series of data fields or any other data structure.Association of certain data may be accomplished through any desired dataassociation technique such as those known or practiced in the art. Forexample, the association may be accomplished either manually orautomatically. In accordance with one aspect of the system, any suitabledata storage technique may be utilized to store data without a standardformat. In one exemplary embodiment, the ability to store a wide varietyof information in different formats is facilitated by storing theinformation as a BLOB. The BLOB method may store data sets as ungroupeddata elements formatted as a block of binary via a fixed memory offsetusing one of fixed storage allocation, circular queue techniques, orbest practices with respect to memory management (e.g., paged memory,least recently used, etc.). As stated above, server repository 104,application repository 106, and/or other databases store data withoutregard to a common format. However, in one exemplary implementation ofthe system, the data set (e.g., BLOB) may be annotated in a standardmanner. The annotation may comprise a short header, trailer, or otherappropriate indicator related to each data set that is configured toconvey information useful in managing the various data sets.

The data set annotation may also be used for other types of statusinformation as well as various other purposes. For example, the data setannotation may include security information establishing access levels.The access levels may, for example, be configured to permit only certainindividuals, levels of employees, companies, or other entities to accessdata sets, or to permit access to specific data sets based on thetransaction, merchant, issuer, consumer, customer or the like.Furthermore, the security information may restrict/permit only certainactions such as accessing, modifying, and/or deleting data. In oneexample, the data set annotation indicates that only the data set owneror the user are permitted to delete a data set, various identified usersmay be permitted to access the data set for reading, and others arealtogether excluded from accessing the data set. However, other accessrestriction parameters may also be used allowing various entities toaccess a data set with various permission levels as appropriate.

Server repository 104, application repository 106, and/or otherdatabases described herein contemplate a data storage arrangementwherein the header or trailer, or header or trailer history, of the datais stored on the transaction instrument in relation to the appropriatedata. One skilled in the art will also appreciate that, for securityreasons, any databases, systems, devices, servers or other components ofserver repository 104, application repository 106, and/or otherdatabases described herein may consist of any combination thereof at asingle location or at multiple locations, wherein each database orsystem includes any of various suitable security features, such asfirewalls, access codes, encryption, decryption, compression,decompression, and/or the like.

The software elements disclosed herein may be loaded onto a generalpurpose computer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructionsthat execute on the computer or other programmable data processingapparatus create means for implementing the functions specified in theflowchart block or blocks. These computer program instructions may alsobe stored in a computer-readable memory that can direct a computer orother programmable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function specified in the flowchart block or blocks.The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

FIG. 2 illustrates a flow chart of an example method 200 for calculatingEOL target for a server, according to various embodiments of the presentdisclosure. As can be seen, the building of the EOL target used manyfactors in combination to arrive at its calculation. This is an additiveprocess which used information provided and retrieved to calculate theEnd of Life target date. For example, in step S202, processing module102 may access server installation dates for each server from serverrepository 104. In step S204, processing module 102 may accessinformation about the operating systems running on each server.Processing module 102 may access the information from server repository104. Processing module 102 determines the applications being processedby each server.

In step S206, processing module 102 accesses SOX scores designated toeach of the applications being processed by each server of the pluralityof servers. For instance, processing module 102 may accesses the SOXscores from application repository 106. The SOX score may be designatedto the applications based on the applications' association with SarbanesOxley Act of 2002. In one example implementation, a SOX indicator may beapplied to each of the applications. The SOX indicator indicates whetherthe application is active, inactive or not SOX critical. Based on SOXindicator of the application, the SOX score may be assigned to theapplication. In one example implementation, SOX score for applicationwith ‘active’ SOX indicator may be in a range of about 80 to about 100,and SOX score for application with SOX indicators ‘inactive’ and ‘notSOX critical’, may be in a range between about 0 and about 20. The SOXscores as discussed above are for illustrative purposes, the actualvalues may vary based on the organizational needs.

In step S208, processing module 102 accesses a data security scoreattributed to an application processed by each server. For instance,processing module 102 may access the data security score fromapplication repository 106. The application may be assigned with thedata security score based on assigned scaled weight of security neededfor the application running on the server. The applications may beclassified into public, business confidential, restricted and secretbased on the weight of the security needed. The applications classifiedas public may have a least security weight, while the applicationsclassified as secret may have a maximum security weight. The applicationclassified as public may be attributed with data security score in arange of about 0 to about 20, the application classified as businessconfidential may be attributed with data security score in a range ofabout in a range of about 20 to about 40. Similarly, the applicationclassified as restricted may be attributed with data security score in arange of about 40 to about 80, and the application classified asbusiness secret may be attributed with data security score in a range ofabout 80 to about 100 as the data security score. The attributed valuesas discussed above are for illustrative purposes, and the actual valuesmay vary based on the organizational needs.

In step S210, processing module 102 generates an application criticalityscore for each of the applications based on the SOX score and the datasecurity score of the corresponding applications. Processing module 102may generate the application criticality score of an application bycalculating a weighted sum of the SOX score and the data security score,where the weights may be set depending upon individual needs of theorganization. The resulting application criticality score indicates thecriticality of the application. In various embodiments, the applicationcriticality score for any application less than or equal to predefinedthreshold value (for example, 50) indicates that the application is notcritical. The application criticality score for any application greaterthan the threshold value indicates that the application criticality ishigh.

In step S212, processing module 102 determines a value for each of theplurality of applications running on the servers using a matrix, wherethe operating system platform of the application processed by eachserver is mapped with the application criticality of the applicationprocessed by the each server. The matrix provides values correspondingto the operating system platform based on the application criticalityfor the application running on corresponding operating system platform.The values may represent the number years after which the uplifting isdue. An example matrix according to various embodiments is providedbelow.

TABLE 1 Platform Low High Linux 5 4 Unix-AIX 6 5 Unix-Sun 5 4 Windows 54 Unknown/Other 6 5

According to the examples provided in Table 1, the first row indicatesthat the designated year for uplifting of an application running on aLinux operating system platform, which has a low applicationcriticality, is the fifth year from the date of installation. Thedesignated year for uplifting is the fourth year for an applicationrunning on the Linux operating system platform, which has a highapplication criticality. The second row indicates that designated yearfor uplifting is the sixth year for an application running on Unix-AIXoperating system platform, which has a low application criticality. Thedesignated year for uplifting is the fifth year for an applicationrunning on the Unix-AIX operating system platform, which has a highapplication criticality. The third row indicates that designated yearfor uplifting is the fifth year for an application running on Unix-Sunoperating system platform, which has a low application criticality. Thedesignated year for uplifting is the fourth year for an applicationrunning on the Unix-Sun operating system platform, which has a highapplication criticality. Other values are apparent as illustrated intable. The values provided in the matrix are for illustrative purposes;the actual values may depend and vary on the organizational needs.

The matrix may be derived depending upon individual needs of theorganization. According to various embodiments, the organization mayderive the matrix based on an understanding of life cycle of operatingsystems in the market, advancement in internal and externaltechnologies, need for migration, the ease of migration, the applicationcriticality and/or the like. The matrix may indicate a value thatrepresent the number years after which the uplifting is due. Accordingto various embodiments, if the application criticality is high, theorganization may set a lower value. If the application criticality islow, the organization may set a higher value.

In step S214, processing module 102 calculates the EOL target date ofeach of the servers using the calculated designated year for upliftingfrom the installation date of each the server. Consider an example:Server A may be installed on 1 Jan. 2010, having a Linux operatingsystem supporting an active application. The SOX score for the activeapplication (with SOX indicator ‘active’) may be set as, for example,100. The application may be a proprietary application having tradesecret algorithm for performing an operation in the organization.Accordingly, data security score for the application may be set as 100.Processing module 102 may generate the application criticality score bycalculating the weighted sum of the SOX score and the data securityscore. In the current example, the SOX score and the data security scoremay be assigned 50% weight each. Thus, the application criticality scoreis 100 indicating that the application criticality is high. Processingmodule 102 may determine a value from, for example, the matrix of table1, by comparing the operating system platform of the application withthe application criticality. The value represent the number years fromthe date of installation after which the uplifting is due. In thecurrent example, processing module 102 may determine that the EOL targetdate for server A is four (4) years from date of installation, that is,1 Jan. 2014. Although, the values/scores shown above are discretevalues, the values may be continuous values as well.

FIG. 3 depicts an example method 300 for prioritizing uplifts for eachof the servers to create a priority according to various embodiments.Based on the weights of various characteristics in combination, apriority score may be calculated. The total, priority score, may bebased on values set by the organization in combination. In step S302,processing module 102 accesses server characteristics of each serverfrom server repository 104. The server characteristics may includevirtual or physical server designations of the servers. The virtualserver designations of the servers include virtual servers or VSS. Thephysical server designations of the servers include ‘V parent’ or‘physical’ servers. In step S304, processing module 102 determinesuptime reliability score for each of the servers by calculating aweighted sum of one or more of values representing age of the servers,server utilization, the application being processed by each server'scriticality, the age of manufacturer's hardware model for each server,the hardware warranty status for each server, availability of operatingsystem support for each servers, and the like. The weights may be setdepending upon individual needs of the organization. The uptimereliability score may be a range of scores that indicate the reliabilityof an element. In one example implementation, the uptime reliabilityscore of one (1) may indicate high reliability, five (5) may indicatelow reliability, and zero (0) may indicate unusable data or omit factordue to lack of data. Although, the values are illustrated to be discretevalues, the values can also be in continues values.

The value representing the age of the servers may be obtained based onrelationship between server age and component failure. These values maybe stored/maintained in a table or database. Statistically, it may befound that x86 based servers experience a component failure in an age0-3 years, 50% chances of component failures in the age of 3-5 years and100% chance of component failures in the age 5 years and above.Correspondingly, the value representing the age of servers may beassigned based on age of servers. According to various embodiments, one(1) may be assigned as the value that represents servers of age 0-3years, three (3) for servers of age 3-5 years, and five (5) for serversof age 5-t years. Zero (0) may be assigned as the value for servers ofunknown age. Processing module 102 may obtain the value representing theage of the servers from server repository 104.

The value representing the server utilization may be based oninformation on utilization of servers. According to various embodiments,one (1) may be assigned as an value representing the servers that areless utilized, five (5) for servers that are highly utilized, and zero(0) for servers of which the utilization is not known. Further, thevalue representing application being processed by server's criticalitymay be based on the server's criticality. One (1) may be assigned as anvalue for applications processed by servers that are not critical, five(5) for applications that are processed by servers that are highlycritical, and zero (0) for applications that are processed by severs ofwhich criticality is not known. Processing module 102 may obtain thevalue representing the server utilization and application beingprocessed by server's criticality, from server repository 104.

The value representing the age of manufacturer's hardware model for eachserver may be based on end of service life (EOSL) data of the servers.According to various embodiments, one (1) may be assigned as a value forservers that are within useful service life, five (5) for servers thatare after EOSL and zero (0) for servers having no manufacture definedEOSL. The value representing hardware warranty status for each servermay be based on availability of the hardware warranty for each of theservers. One (1) may be assigned as a value for servers that are coveredby warranty, five (5) for servers that are not covered by warranty andzero (0) for servers having no warranty information. The valuerepresenting the availability of operating system support for eachserver may be based on information from the operating systemmanufacturer. One (1) is assigned as a value for servers that have theoperating system manufacturer support, five (5) for servers that have nooperating system manufacturer support and zero (0) for servers havingoperating system with no information about operating system manufacturersupport. The values discussed above are for illustrative purposes, andthe actual values may depend and vary on the organizational needs.Processing module 102 may obtain the value representing the age ofmanufacturer's hardware model for each server, hardware warranty statusand the availability of operating system support, from server repository104.

In step S306, processing module 102 determines a flexibility score ofeach of the servers. The flexibility score may be based on age of themanufacturer's hardware model and alignment with current hardwarestandards of an organization running the applications on each server.Processing module 102 determines the flexibility score for each of theservers by calculating a weighted sum of values representing the age ofthe manufacturer's hardware model and alignment with current hardwarestandards of an organization running applications on each server foreach of the servers. The weights may be set depending upon individualneeds of the organization. According to various embodiments, aflexibility score of one (1) may indicate high flexibility, five (5) mayindicate low flexibility, and zero (0) may indicate unknown flexibility.The value representing the age of the manufacturer's hardware model mayindicate whether the server is within the EOSL. A value representing theage of the manufacturer's hardware model for servers that are within theEOSL may be set to one (1), and value representing the age of themanufacturer's hardware model for servers that are not within the EOSLmay be set to five (5). The value representing the age of themanufacturer's hardware model for servers that have no information aboutEOSL may be set to zero (0). The value representing the alignment withcurrent hardware standards of an organization running applications oneach server may be based on flexibility of the manufacturer's hardwareto align with the current hardware standards of the organization. Valuesin the range of one (1) to five (5) may be assigned to the servers basedon flexibility of the manufacturer's hardware to align with the currenthardware standards of the organization. A value of one (1) may assignedto the manufacturer's hardware that has a very high flexibility to bealigned with current hardware standards of an organization runningapplications on each server. A value of five (5) may be assigned to themanufacturer's hardware has least flexibility to be aligned with currenthardware standards of an organization running applications on eachserver. Processing module 102 may obtain the value representing age ofthe manufacturer's hardware model and alignment with current hardwarestandards of an organization running the applications on each server,from server repository 104.

In step S308, processing module 102 determines a maintenance cost scoreof each of the servers. The maintenance cost score may indicate themaintenance cost of the server and/or applications running on theserver. The maintenance cost score may be based on the alignment withcurrent hardware standards of an organization running applications oneach server, orphaned server details and/or power consumption.Processing module 102 may determine the maintenance cost scores bycalculating weighted sum of values representing the alignment withcurrent hardware standards of an organization running applications oneach server, orphaned server details and/or power consumption for eachof the servers. The weights may be set depending upon individual needsof the organization. According to various embodiments, a maintenancecost score of one (1) may indicate a low maintenance cost, five (5) mayindicate a high maintenance cost, and zero (0) may indicate unknownmaintenance cost or no value.

The value representing the alignment with current hardware standards ofan organization running applications on each server may indicate thescale of expense involved in aligning the server hardware to thehardware standards of the organization. According to variousembodiments, values in the range of one (1) to five (5) may be assignedto the servers based on cost involved in aligning the server hardware tothe hardware standards of the organization. A value of one (1) mayindicate that the cost of aligning the server hardware to the hardwarestandards of the organization is very low. A value of five (5) mayindicate that the cost of aligning the server hardware to the hardwarestandards of the organization is very high. Other intermediate valuesindicate costs relative to values of one (1) and five (5). Processingmodule 102 may obtain the value representing the alignment with currenthardware standards of an organization running applications on eachserver from server repository 104.

The values representing the orphaned server may be based on applicationsbeing decommissioned or moved to another server. According to variousembodiments, the value of one (1) may be assigned to server forapplications being continued, five (5) for the servers whereapplications are decommissioned or moved, and zero (0) for servershaving no applications. The values representing power consumption ofserver may be based on power being consumed. The value of one (1) may beassigned to servers consuming low power, five (5) for the servers thatconsume high power, and zero (0) for servers having no data about powerconsumption. Processing module 102 may obtain the value representing theorphaned server from server repository 104.

In step S310, processing module 102 generates a priority score for eachof the servers. The priority score may be based on the servercharacteristics, the uptime reliability score, the flexibility score andthe maintenance cost scores of the servers. If the server is a virtualserver, processing module 102 may assign a predetermined score as thepriority score. If the server is physical, processing module 102 maydetermine the priority score based on weighted sum of the uptimereliability scores, the flexibility score and/or the maintenance costscore. The weights may be set depending upon individual needs of theorganization. According to various embodiments, the weight assigned touptime reliability score may be in the range of around 50-70%, theweight assigned to the flexibility score may be in the range of around10-30%, and the weight assigned to the maintenance cost score may be inthe range of around 10-30%. Again, the values provided herein are forillustrative purposes, the actual values may vary based on theorganizational needs.

In step S312, based on the priority score, processing module 102generates the priority for uplifts. According to various embodiments,the priority may be generated based on multiple threshold scores. Basedon priority score falling between the threshold scores, processingmodule 102 may indicate that the server may have to be upliftedaccording to a year from the current year corresponding to the thresholdscore.

In instances where one or more servers are already marked for uplift ingeneral organization infrastructure related programs, abrupt failures,and the like, processing module 102 may not consider those servers forpriority. The organization infrastructure related programs may includeserver decommissioning, application rationalization, applicationdecommissioning, and/or application infrastructure uplift for allapplications on the server. In addition, a server may be marked foruplift based on history of faults. Based on severity of faults, serversmay be marked for uplift or decommission.

An example for determining priority for four (4) servers: server A,server B, server C and server D is described herein. Priority for anuplift may be determined based on priority score. The priority score maybe based on weighted sum of the uptime reliability scores, theflexibility score and the maintenance cost score.

The uptime reliability score may be a weighted sum of valuesrepresenting two or more of age of server, server utilization,applications being processed by each server's criticality, age ofmanufacturer's hardware model for each server, hardware warranty statusfor each server and/or availability of operating system support for eachserver. In current example, date of installation is 1 Jan. 2010 for ofserver A, 1 Jan. 2007 for server B, 1 Jan. 2008 for server C, and 3 Jan.2010 for server D. Assuming that the current year is 2012, in thecurrent example, the age of server A is two (2) years, the age of serverB is five (5) years, the age of server C is four (4) years, and the ageof server D is two (2) years. Correspondingly, the value representingthe age of server may be one (1) for server A, five (5) for server B,three (3) for server C and one (1) for server D. Further, servers A-Dmay be highly utilized. Accordingly, the value of five (5) may beassigned to the servers A-D.

According to various embodiments, application criticality may be ‘high’for servers A and server B, and ‘low’ for server C and server D.Correspondingly, the value representing server A and server B is one(1). The value representing server C and server D is five (5). Further,the age of manufacturer's hardware model is ‘before EOSL’ for servers Aand server D, and ‘after EOSL’ for server B and C. Correspondingly, thevalues representing the age of manufacturer's hardware model is one (1)for server A and server D, and five (5) for servers B and server C.Server A and server D may be in warranty, and server B and server C maybe out of warranty. Thus, the values representing warranty status is one(1) for server A and server D, and five (5) for servers B and server C.The operating system of server A and D is Linux, the operating system ofserver B is Windows, and the operating system of server C is AIX.Further, server A and server C have manufacturer's support forrespective operating systems, whereas server B and server D may not havemanufacturer's support. Thus, the values representing manufacturer'ssupport is one (1) for server A and server C, and five (5) for servers Band server D. Using the values representing the two or more of age ofserver, the server utilization, the applications being processed by eachserver's criticality, the age of manufacturer's hardware model for eachserver, the hardware warranty status for each server and theavailability of operating system support for each server, the uptimereliability score may be calculated as 1.8, 4.2, 3.8 and 2.6, for serverA, server B, server C, and server D, respectively. In the currentexample, the weight may be 20% for the values representing the two ormore of age of server, the applications being processed by each server'scriticality, the age of manufacturer's hardware model for each server,and the hardware warranty status for each server and the availability ofoperating system support for each server. The weight may be 0% for thevalues representing the server utilization.

The flexibility score may be calculated based on age of themanufacturer's hardware model and alignment with current hardwarestandards of an organization running applications on each server. Theflexibility score may be weighted sum of values representing the age ofthe manufacturer's hardware model and the alignment with currenthardware standards of an organization running applications on eachserver. As described herein, the values representing the age ofmanufacturer's hardware model is one (1) for server A and server D, andfive (5) for servers B and server C. The server hardware of server A andserver D may be highly flexible to be aligned with the current hardwarestandards of the organization. The server hardware of server B andserver C may have low flexibility to be aligned with the currenthardware standards of the organization. Correspondingly, the valuesrepresenting the alignment with current hardware standards of anorganization running applications on each server is one (1) for server Aand server D, and five (5) for servers B and server C. In the currentexample, the weights may be 50% each for the values representing the ageof the manufacturer's hardware model and the alignment with currenthardware standards of an organization running applications on eachserver. Using the values above, the flexibility score may be 1 forserver A and server D. The flexibility score may be 5 for server B andserver C.

The maintenance cost score may be a weighted sum of values representingthe alignment with current hardware standards of an organization runningapplications on each server, orphaned server details and/or powerconsumption. As described above, the values representing the alignmentwith current hardware standards of an organization running applicationson each server is one (1) for server A and server D, and five (5) forservers B and server C. Further, servers A-D may have applications.Thus, the values representing orphaned server is one (1) for serversA-D. Server A and server D may consume power less than a thresholdvalue. Server B and server C may consume power higher than a thresholdvalue. Correspondingly, the values representing power consumption is one(1) for servers A-D, and five (5) for servers B-C. In the currentexample, the weight may be 25% each for the values representing thealignment with current hardware standards of an organization runningapplications on each server, orphaned server details, and 50% for valuesrepresenting power consumption. Using the values above, the maintenancecost score may be one (1) for server A and server D. The maintenancecost score may be three (3) for server B and server C.

Priority score may be calculated based on server characteristics, theuptime reliability score, the flexibility score and the maintenance costscore. If a server has virtual characteristics, the server may beassigned with a predetermined priority score. In the current example,server C may be a virtual server, thus the priority score may be 1.Other servers are physical servers. The priority score for physicalserver may be calculated based on weighted sum of the uptime reliabilityscore, the flexibility score and the maintenance cost score. In thecurrent example, the weight assigned to uptime reliability score is 50%,the weight assigned to the flexibility score is 25%, and the weightassigned to the maintenance cost score is 25%. Thus, priority scores maybe 1.4, 4.3 and 1.8 for servers A-B, server C and server D,respectively. In the example embodiment, if the priority score generatedfor a server is less than 5 and greater than 4, the server may beuplifted within the current year. Similarly, if the priority scoregenerated for a server is in between 4 and 3, the server may be upliftedin the next year. If the priority score generated for a server is inbetween 3 and 2, the server may be uplifted in the 2nd year from thecurrent year. If the priority score generated for a server is in between2 and 1, the server may be uplifted in the 3rd year from the currentyear. If the priority score generated for a server is less than and/orequal to 1, the server may be uplifted in the 4th year from the currentyear. Assuming the current year to be 2012, server A is listed foruplifting after 1 Jan. 2014, server B is listed for uplifting in thecurrent year (2012), server C may is listed for uplifting 1 Jan. 2014and server D may be uplifted after 1 Jan. 2014. Again, the values andweights are provided for illustrative purposes, the actual values andweights may vary based on the organizational needs.

FIG. 4 is a flowchart illustrating an example process 400 for managementof the processing resources, according to various embodiments of thepresent disclosure. In step S402, processing module 102 accessesvariables for managing processing resource. According to variousembodiments, processing module 102 may access variables from serverrepository 104 and application repository. The variables may facilitatecompiling a prioritized list of servers of the plurality of servers. Instep S404, processing module 102 determines the EOL targets for theplurality of servers. Processing module 102 may determine the EOLtargets based on first set of technical and business parameters.Processing module 102 may determine the EOL targets based on the firstset of technical and business parameters. The first set of technical andbusiness parameters include the installation date of servers,information associated with operating system implemented on each of theservers, an application criticality score based on a combination of aSarbanes Oxley score and/or a data security score of an applicationprocessed by each server. In step S406, processing module 103prioritizes uplifts of each server of the plurality of servers.Processing module 102 may prioritizes uplifts based on the second set oftechnical and business parameters. The second set of technical andbusiness parameters may include server characteristics, uptimereliability score, flexibility, and/or a maintenance cost score.

The present disclosure (i.e., processing module 102, process 200,process 300, process 400, or any part(s) or function(s) thereof) may beimplemented using hardware, software or a combination thereof, and maybe implemented in one or more computer systems or other processingsystems. However, the manipulations performed by the system were oftenreferred to in terms, such as comparing or checking, which are commonlyassociated with mental operations performed by a human operator. No suchcapability of a human operator is necessary, or desirable in most cases,in any of the operations described herein, which form a part of thedisclosure. Rather, the operations are machine operations. Usefulmachines for performing the operations in the system may includegeneral-purpose digital computers or similar devices.

Computer system 500 includes at least one processor, such as a processor502. Processor 502 is connected to a communication infrastructure 504,for example, a communications bus, a cross over bar, a network, and thelike. Various software embodiments are described in terms of thisexemplary computer system 500. After reading this description, it willbecome apparent to a person skilled in the relevant art(s) how toimplement the disclosure using other computer systems and/orarchitectures.

Computer system 500 includes a display interface 506 that forwardsgraphics, text, and other data from the communication infrastructure 504for display on a display unit 508.

Computer system 500 further includes a main memory 510, such as randomaccess memory (RAM), and may also include a secondary memory 512.Secondary memory 512 may further include, for example, a hard disk drive514 and/or a removable storage drive 516, representing a floppy diskdrive, a magnetic tape drive, an optical disk drive, etc. Removablestorage drive 516 reads from and/or writes to a removable storage unit518 in a well known manner. Removable storage unit 518 may represent afloppy disk, magnetic tape or an optical disk, and may be read by andwritten to by removable storage drive 516. As will be appreciated,removable storage unit 518 includes a computer usable storage mediumhaving stored therein, computer software and/or data.

In accordance with various embodiments, secondary memory 512 may includeother similar devices for allowing computer programs or otherinstructions to be loaded into computer system 500. Such devices mayinclude, for example, a removable storage unit 520, and an interface522. Examples of such may include a program cartridge and cartridgeinterface (such as that found in video game devices), a removable memorychip (such as an erasable programmable read only memory (EPROM), orprogrammable read only memory (PROM)) and associated socket, and otherremovable storage unit 520 and interfaces 522, which allow software anddata to be transferred from removable storage unit 520 to computersystem 500.

Computer system 500 may further include a communication interface 524.Communication interface 524 allows software and data to be transferredbetween the computer system 500 and external devices. Examples ofcommunication interface 524 include, but may not be limited to a modem,a network interface (such as an Ethernet card), a communications port, aPersonal Computer Memory Card International Association (PCMCIA) slotand card, and the like. Software and data transferred via thecommunication interface 524 are in the form of a plurality of signals,hereinafter referred to as signals 526, which may be electronic,electromagnetic, optical or other signals capable of being received bythe communication interface 524. Signals 526 are provided tocommunication interface 524 via a communication path (e.g., channel)528. Communication path 528 carries signals 526 and may be implementedusing wire or cable, fiber optics, a telephone line, a cellular link, aradio frequency (RF) link and other communication channels.

In this document, the terms “computer program medium” and “computerusable medium” are used to generally refer to media such as removablestorage drive 516, a hard disk installed in hard disk drive 514, signals526, and the like. These computer program products provide software tocomputer system 500. The present disclosure is directed to such computerprogram products.

Computer programs (also referred to as computer control logic) arestored in main memory 510 and/or secondary memory 512. Computer programsmay also be received via the communication infrastructure 504. Suchcomputer programs, when executed, enable computer system 500 to performthe features of the present disclosure, as discussed herein. Inparticular, the computer programs, when executed, enable processor 502to perform the features of the present disclosure. Accordingly, suchcomputer programs represent controllers of computer system 500.

In accordance with various embodiments, software may be stored in acomputer program product and loaded into computer system 500 using theremovable storage drive 516, hard disk drive 514 or communicationinterface 524. The control logic (software), when executed by processor502, causes processor 502 to perform the functions of the presentdisclosure as described herein.

In various embodiments, the present disclosure is implemented primarilyin hardware using, for example, hardware components such as applicationspecific integrated circuits (ASIC). Implementation of the hardwarestate machine so as to perform the functions described herein will beapparent to persons skilled in the relevant art(s).

According to various embodiments, the aspects of the present disclosureare implemented using a combination of both the hardware and thesoftware. As used herein, the term “server” as described herein mayinclude server hardware, server software, applications and/or serviceshosted by the server, and/or combinations thereof. The organization mayalso use one or more database systems communicatively coupled to the oneor more servers for storing various data, such as, organizational data,merchant data, customer data and/or the like.

The various system components discussed herein may include one or moreof the following: a host server or other computing systems including aprocessor for processing digital data; a memory coupled to the processorfor storing digital data; an input digitizer coupled to the processorfor inputting digital data; an application program stored in the memoryand accessible by the processor for directing processing of digital databy the processor; a display device coupled to the processor and memoryfor displaying information derived from digital data processed by theprocessor; and a plurality of databases. Various databases used hereinmay include: client data; merchant data; financial institution data;and/or like data useful in the operation of the system. As those skilledin the art will appreciate, user computer may include an operatingsystem (e.g., Windows NT, Windows 95/98/2000, Windows XP, Windows Vista,Windows 7, OS2, UNIX, Linux, Solaris, MacOS, etc.) as well as variousconventional support software and drivers typically associated withcomputers.

The present system or any part(s) or function(s) thereof may beimplemented using hardware, software or a combination thereof and may beimplemented in one or more computer systems or other processing systems.However, the manipulations performed by embodiments were often referredto in terms, such as matching or selecting, which are commonlyassociated with mental operations performed by a human operator. No suchcapability of a human operator is necessary, or desirable in most cases,in any of the operations described herein. Rather, the operations may bemachine operations. Useful machines for performing the variousembodiments include general purpose digital computers or similardevices.

In fact, in various embodiments, the embodiments are directed toward oneor more computer systems capable of carrying out the functionalitydescribed herein. The computer system includes one or more processors,such as processor. The processor is connected to a communicationinfrastructure (e.g., a communications bus, cross-over bar, or network).Various software embodiments are described in terms of this exemplarycomputer system. After reading this description, it will become apparentto a person skilled in the relevant art(s) how to implement variousembodiments using other computer systems and/or architectures. Computersystem can include a display interface that forwards graphics, text, andother data from the communication infrastructure (or from a frame buffernot shown) for display on a display unit.

Computer system also includes a main memory, such as for example randomaccess memory (RAM), and may also include a secondary memory. Thesecondary memory may include, for example, a hard disk drive and/or aremovable storage drive, representing a floppy disk drive, a magnetictape drive, an optical disk drive, etc. The removable storage drivereads from and/or writes to a removable storage unit in a well-knownmanner. Removable storage unit represents a floppy disk, magnetic tape,optical disk, etc. which is read by and written to by removable storagedrive. As will be appreciated, the removable storage unit includes acomputer usable storage medium having stored therein computer softwareand/or data.

The computer system may also include a communications interface.Communications interface allows software and data to be transferredbetween computer system and external devices. Examples of communicationsinterface may include a modem, a network interface (such as an Ethernetcard), a communications port, a Personal Computer Memory CardInternational Association (PCMCIA) slot and card, etc. Software and datatransferred via communications interface are in the form of signalswhich may be electronic, electromagnetic, optical or other signalscapable of being received by communications interface. These signals areprovided to communications interface via a communications path (e.g.,channel). This channel carries signals and may be implemented usingwire, cable, fiber optics, a telephone line, a cellular link, a radiofrequency (RF) link, wireless and other communications channels.

Computer programs (also referred to as computer control logic) arestored in main memory and/or secondary memory. Computer programs mayalso be received via communications interface. Such computer programs,when executed, enable the computer system to perform the features asdiscussed herein. In particular, the computer programs, when executed,enable the processor to perform the features of various embodiments.Accordingly, such computer programs represent controllers of thecomputer system.

In various embodiments, software may be stored in a computer programproduct and loaded into computer system using removable storage drive,hard disk drive or communications interface. The control logic(software), when executed by the processor, causes the processor toperform the functions of various embodiments as described herein. Invarious embodiments, hardware components such as application specificintegrated circuits (ASICs). Implementation of the hardware statemachine so as to perform the functions described herein will be apparentto persons skilled in the relevant art(s).

As used herein, the term “network” includes any cloud, cloud computingsystem or electronic communications system or method which incorporateshardware and/or software components. Communication among the parties maybe accomplished through any suitable communication channels, such as,for example, a telephone network, an extranet, an intranet, Internet,point of interaction device (point of sale device, personal digitalassistant (e.g., iPhone®, Palm Pilot®, Blackberry®), cellular phone,kiosk, etc.), online communications, satellite communications, off-linecommunications, wireless communications, transponder communications,local area network (LAN), wide area network (WAN), virtual privatenetwork (VPN), networked or linked devices, keyboard, mouse and/or anysuitable communication or data input modality. Moreover, although thesystem is frequently described herein as being implemented with TCP/IPcommunications protocols, the system may also be implemented using IPX,Appletalk, IP-6, NetBIOS, OSI, any tunneling protocol (e.g. IPsec, SSH),or any number of existing or future protocols. If the network is in thenature of a public network, such as the Internet, it may be advantageousto presume the network to be insecure and open to eavesdroppers.Specific information related to the protocols, standards, andapplication software utilized in connection with the Internet isgenerally known to those skilled in the art and, as such, need not bedetailed herein. See, for example, DILIP NAIK, INTERNET STANDARDS ANDPROTOCOLS (1998); JAVA 2 COMPLETE, various authors, (Sybex 1999);DEBORAH RAY AND ERIC RAY, MASTERING HTML 4.0 (1997); and LOSHIN, TCP/IPCLEARLY EXPLAINED (1997) and DAVID GOURLEY AND BRIAN TOTTY, HTTP, THEDEFINITIVE GUIDE (2002), the contents of which are hereby incorporatedby reference.

The various system components may be independently, separately orcollectively suitably coupled to the network via data links whichincludes, for example, a connection to an Internet Service Provider(ISP) over the local loop as is typically used in connection withstandard modem communication, cable modem, Dish networks, ISDN, DigitalSubscriber Line (DSL), or various wireless communication methods, see,e.g., GILBERT HELD, UNDERSTANDING DATA COMMUNICATIONS (1996), which ishereby incorporated by reference. It is noted that the network may beimplemented as other types of networks, such as an interactivetelevision (ITV) network. Moreover, the system contemplates the use,sale or distribution of any goods, services or information over anynetwork having similar functionality described herein.

“Cloud” or “Cloud computing” includes a model for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, servers, storage, applications, and services)that can be rapidly provisioned and released with minimal managementeffort or service provider interaction. Cloud computing may includelocation-independent computing, whereby shared servers provideresources, software, and data to computers and other devices on demand.For more information regarding cloud computing, see the NIST's (NationalInstitute of Standards and Technology) definition of cloud computing athttp://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf (lastvisited June 2012), which is hereby incorporated by reference in itsentirety.

The system and method may be described herein in terms of functionalblock components, screen shots, optional selections and variousprocessing steps. It should be appreciated that such functional blocksmay be realized by any number of hardware and/or software componentsconfigured to perform the specified functions. For example, the systemmay employ various integrated circuit components, e.g., memory elements,processing elements, logic elements, look-up tables, and the like, whichmay carry out a variety of functions under the control of one or moremicroprocessors or other control devices. Similarly, the softwareelements of the system may be implemented with any programming orscripting language such as C, C++, C#, Java, JavaScript, VBScript,Macromedia Cold Fusion, COBOL, Microsoft Active Server Pages, assembly,PERL, PHP, awk, Python, Visual Basic, SQL Stored Procedures, PL/SQL, anyUNIX shell script, and extensible markup language (XML) with the variousalgorithms being implemented with any combination of data structures,objects, processes, routines or other programming elements. Further, itshould be noted that the system may employ any number of conventionaltechniques for data transmission, signaling, data processing, networkcontrol, and the like. Still further, the system could be used to detector prevent security issues with a client-side scripting language, suchas JavaScript, VBScript or the like. For a basic introduction ofcryptography and network security, see any of the following references:(1) “Applied Cryptography: Protocols, Algorithms, And Source Code In C,”by Bruce Schneier, published by John Wiley & Sons (second edition,1995); (2) “Java Cryptography” by Jonathan Knudson, published byO'Reilly & Associates (1998); (3) “Cryptography & Network Security:Principles & Practice” by William Stallings, published by Prentice Hall;all of which are hereby incorporated by reference.

As will be appreciated by one of ordinary skill in the art, the systemmay be embodied as a customization of an existing system, an add-onproduct, a processing apparatus executing upgraded software, astand-alone system, a distributed system, a method, a data processingsystem, a device for data processing, and/or a computer program product.Accordingly, any portion of the system or a module may take the form ofa processing apparatus executing code, an internet based embodiment, anentirely hardware embodiment, or various embodiments combining aspectsof the internet, software and hardware. Furthermore, the system may takethe form of a computer program product on a computer-readable storagemedium having computer-readable program code means embodied in thestorage medium. Any suitable computer-readable storage medium may beutilized, including hard disks, CD-ROM, optical storage devices,magnetic storage devices, and/or the like.

The system and method is described herein with reference to screenshots, block diagrams and flowchart illustrations of methods, apparatus(e.g., systems), and computer program products according to variousembodiments. It will be understood that each functional block of theblock diagrams and the flowchart illustrations, and combinations offunctional blocks in the block diagrams and flowchart illustrations,respectively, can be implemented by computer program instructions.

Referring now to FIGS. 1-4 the process flows and screenshots depictedare merely embodiments and are not intended to limit the scope of thedisclosure. For example, the steps recited in any of the method orprocess descriptions may be executed in any order and are not limited tothe order presented.

Accordingly, functional blocks of the block diagrams and flowchartillustrations support combinations of means for performing the specifiedfunctions, combinations of steps for performing the specified functions,and program instruction means for performing the specified functions. Itwill also be understood that each functional block of the block diagramsand flowchart illustrations, and combinations of functional blocks inthe block diagrams and flowchart illustrations, can be implemented byeither special purpose hardware-based computer systems which perform thespecified functions or steps, or suitable combinations of specialpurpose hardware and computer instructions. Further, illustrations ofthe process flows and the descriptions thereof may make reference touser windows, webpages, websites, web forms, prompts, etc. Practitionerswill appreciate that the illustrated steps described herein may comprisein any number of configurations including the use of windows, webpages,web forms, popup windows, prompts and the like. It should be furtherappreciated that the multiple steps as illustrated and described may becombined into single webpages and/or windows but have been expanded forthe sake of simplicity. In other cases, steps illustrated and describedas single process steps may be separated into multiple webpages and/orwindows but have been combined for simplicity.

The term “non-transitory” is to be understood to remove only propagatingtransitory signals per se from the claim scope and does not relinquishrights to all standard computer-readable media that are not onlypropagating transitory signals per se. Stated another way, the meaningof the term “non-transitory computer-readable medium” and“non-transitory computer-readable storage medium” should be construed toexclude only those types of transitory computer-readable media whichwere found in In Re Nuijten to fall outside the scope of patentablesubject matter under 35 U.S.C. §101.

Benefits, other advantages, and solutions to problems have beendescribed herein with regard to specific embodiments. However, thebenefits, advantages, solutions to problems, and any elements that maycause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as critical, required, or essentialfeatures or elements of the disclosure. The scope of the disclosure isaccordingly to be limited by nothing other than the appended claims, inwhich reference to an element in the singular is not intended to mean“one and only one” unless explicitly so stated, but rather “one ormore.” Moreover, where a phrase similar to ‘at least one of A, B, and C’or ‘at least one of A, B, or C’ is used in the claims or specification,it is intended that the phrase be interpreted to mean that A alone maybe present in an embodiment, B alone may be present in an embodiment, Calone may be present in an embodiment, or that any combination of theelements A, B and C may be present in a single embodiment; for example,A and B, A and C, B and C, or A and B and C. Although the disclosureincludes a method, it is contemplated that it may be embodied ascomputer program instructions on a tangible computer-readable carrier,such as a magnetic or optical memory or a magnetic or optical disk. Allstructural, chemical, and functional equivalents to the elements of theabove-described various embodiments that are known to those of ordinaryskill in the art are expressly incorporated herein by reference and areintended to be encompassed by the present claims. Moreover, it is notnecessary for a device or method to address each and every problemsought to be solved by the present disclosure, for it to be encompassedby the present claims. Furthermore, no element, component, or methodstep in the present disclosure is intended to be dedicated to the publicregardless of whether the element, component, or method step isexplicitly recited in the claims. No claim element herein is to beconstrued under the provisions of 35 U.S.C. 112, sixth paragraph, unlessthe element is expressly recited using the phrase “means for.” As usedherein, the terms “comprises”, “comprising”, or any other variationthereof, are intended to cover a non-exclusive inclusion, such that aprocess, method, article, or apparatus that comprises a list of elementsdoes not include only those elements but may include other elements notexpressly listed or inherent to such process, method, article, orapparatus.

In addition, it should be understood that the figures illustrated in theattachments, which highlight the functionality and advantages of thepresent disclosure, are presented for example purposes only. Thearchitecture of the present disclosure is sufficiently flexible andconfigurable, such that it may be utilized (and navigated) in ways otherthan that shown in the accompanying figures.

Further, the purpose of the foregoing Abstract is to enable the U.S.Patent and Trademark Office and the public generally, and especially thescientists, engineers and practitioners in the art who are not familiarwith patent or legal terms or phraseology, to determine quickly from acursory inspection the nature and essence of the technical disclosure ofthe application. The Abstract is not intended to be limiting as to thescope of the present disclosure in any way.

The invention claimed is:
 1. A method comprising: accessing, by acomputer-based system, variables; compiling, by the computer-basedsystem and based on the variables, a prioritized list of servers of aplurality of servers; determining, by the computer-based system andusing an application, end of life targets for the plurality of serversbased on a first set of technical and business parameters ofapplications running on each server of the plurality of servers, whereinthe first set of technical and business parameters of the applicationsare based on the variables, wherein the first set of technical andbusiness parameters comprise an application criticality score based on acombination of a Sarbanes Oxley score and a data security score of anapplication processed by each server, assessing, by the computer-basedsystem and based on a standard, data security of an applicationprocessed by each server of the plurality of servers; scoring, by thecomputer-based system and based on the assessment, the application tocreate a data security score, wherein the data security score includes apublic, business confidential, restricted or secret designation of theapplication processed by each server of the plurality of servers;obtaining, by the computer-based system and from a repository of theserver, a weight for the Sarbanes Oxley score to create a weightedSarbanes Oxley score; obtaining, by the computer-based system and fromthe repository of the server, a weight for the data security score tocreate a weighted data security score; updating, by the computer-basedsystem, the application criticality score based on the weighted SarbanesOxley score and the weighted data security score; adjusting, by thecomputer-based system, the application criticality score based on animportance of the application for an organization, a customer or amerchant; determining, by the computer-based system, an applicationcriticality based on the application criticality score being above apre-determined threshold; comparing, by the computer-based system, anoperating system platform of the application processed by the serverwith the application criticality of the application processed by theserver; determining, by the computer-based system and based on thecomparison, an end of life target for the server; determining, by thecomputer-based system, a designated year to replace the server, based onthe end of life target; prioritizing, by the computer-based system,uplifts of each server of the plurality of servers to create a priority,wherein the prioritizing is based on a second set of technical andbusiness parameters; and removing, by the computer-based system, aserver from the prioritized list of servers based on an indicatorsignifying the server is previously designated to be uplifted, whereinthe indicator is retrieved from at least one of a server repository oran application repository.
 2. The method of claim 1, wherein the upliftsinclude at least one of replacement, refresh, modification, upgrade orupdate to at least one of hardware or software of the server.
 3. Themethod of claim 2, wherein the variables comprise a server install date,the operating system of an application being processed by each server ofthe plurality of servers, a Sarbanes-Oxley score designated to anapplication processed by each server of the plurality of servers, and adata security score attributed to an application processed by eachserver.
 4. The method of claim 3, further comprising budgeting, by thecomputer-based system, uplifts based on the priority.
 5. The method ofclaim 4, further comprising uplifting, by the computer-based system, aserver of the plurality of servers based on the priority.
 6. The methodof claim 5, wherein the Sarbanes Oxley score is based on a SarbanesOxley code designated to each application processed by each server ofthe plurality of servers based on the application's association with theSarbanes Oxley Act of 2002, wherein the Sarbanes Oxley code indicateswhether the application is at least one of active critical application,inactive or not Sarbanes Oxley Act of 2002 critical.
 7. The method ofclaim 6, wherein each server's end of life target is based on a matrixwhere the operating system platform of an application processed by eachserver is compared with an application criticality of applicationprocessed by each server.
 8. The method of claim 7, wherein the datasecurity score is based on an assigned scaled weight of security neededfor each application running on each server of the plurality of servers.9. The method of claim 8, wherein each server's end of life targetcomprises a designated year for uplifting as calculated from theinstallation date of each server of the plurality of servers.
 10. Themethod of claim 9, wherein the second set of technical and businessparameters comprise server characteristics, uptime reliability score,flexibility, and a maintenance cost score.
 11. The method of claim 10,wherein the server characteristics comprise a virtual or physical serverdesignation.
 12. The method of claim 11, wherein the uptime reliabilityscore is based on at least one of the age of each server, each serversutilization, an application being processed by each server'scriticality, age of manufacturer' hardware model for each server,hardware warranty status for each server, or availability of operatingsystem support for each server.
 13. The method of claim 12, wherein theflexibility is based on at least one of the age of the manufacturershardware model or an alignment with current hardware standards of anorganization running applications on each server.
 14. The method ofclaim 13, wherein the maintenance cost score is based on at least one ofalignment with current hardware standards of an organization runningapplications on each server, designation of orphaned servers, or powerconsumption of each server.
 15. The method of claim 14, furthercomprising updating the re-prioritizing the servers based on the startof a new budget term.
 16. The method of claim 15, further comprisingspecifying a server with a history of faults ahead of older servers onan individual basis.
 17. A system comprising: a processor, a tangible,non-transitory memory configured to communicate with the processor, thetangible, non-transitory memory having instructions stored thereon that,in response to execution by the processor, cause the processor toperform operations comprising: accessing, by the processor, variables;compiling, by the processor and based on the variables, a prioritizedlist of servers of a plurality of servers; determining, by the processorand using an application, end of life targets for the plurality ofservers based on a first set of technical and business parameters ofapplications running on each server of the plurality of servers, whereinthe first set of technical and business parameters of the applicationsare based on the variables, wherein the first set of technical andbusiness parameters comprise an application criticality score based on acombination of a Sarbanes Oxley score and a data security score of anapplication processed by each server, assessing, by the processor andbased on a standard, data security of an application processed by eachserver of the plurality of servers; scoring, by the processor and basedon the assessment, the application to create a data security score,wherein the data security score includes a public, businessconfidential, restricted or secret designation of the applicationprocessed by each server of the plurality of servers; obtaining, by theprocessor and from a repository of the server, a weight for the SarbanesOxley score to create a weighted Sarbanes Oxley score; obtaining, by theprocessor and from the repository of the server, a weight for the datasecurity score to create a weighted data security score; updating, bythe processor, the application criticality score based on the weightedSarbanes Oxley score and the weighted data security score; adjusting, bythe processor, the application criticality score based on an importanceof the application for an organization, a customer or a merchant;determining, by the processor, an application criticality based on theapplication criticality score being above a pre-determined threshold;comparing, by the processor, an operating system platform of theapplication processed by the server with the application criticality ofthe application processed by the server; determining, by the processorand based on the comparison, an end of life target for the server;determining, by the processor, a designated year to replace the server,based on the end of life target; prioritizing, by the processor, upliftsof each server of the plurality of servers to create a priority, whereinthe prioritizing is based on a second set of technical and businessparameters; and removing, by the processor, a server from theprioritized list of servers based on an indicator signifying the serveris previously designated to be uplifted, wherein the indicator isretrieved from at least one of a server repository or an applicationrepository.
 18. An article of manufacture including a non-transitory,tangible computer readable storage medium having instructions storedthereon that, in response to execution by a computer-based system formanaging processing resources, cause the computer-based system toperform operations comprising: accessing, by the computer-based system,variables; compiling, by the computer-based system and based on thevariables, a prioritized list of servers of a plurality of servers;determining, by the computer-based system and using an application, endof life targets for the plurality of servers based on a first set oftechnical and business parameters of applications running on each serverof the plurality of servers, wherein the first set of technical andbusiness parameters of the applications are based on the variables,wherein the first set of technical and business parameters comprise anapplication criticality score based on a combination of a Sarbanes Oxleyscore and a data security score of an application processed by eachserver, assessing, by the computer-based system and based on a standard,data security of an application processed by each server of theplurality of servers; scoring, by the computer-based system and based onthe assessment, the application to create a data security score, whereinthe data security score includes a public, business confidential,restricted or secret designation of the application processed by eachserver of the plurality of servers; obtaining, by the computer-basedsystem and from a repository of the server, a weight for the SarbanesOxley score to create a weighted Sarbanes Oxley score; obtaining, by thecomputer-based system and from the repository of the server, a weightfor the data security score to create a weighted data security score;updating, by the computer-based system, the application criticalityscore based on the weighted Sarbanes Oxley score and the weighted datasecurity score; adjusting, by the computer-based system, the applicationcriticality score based on an importance of the application for anorganization, a customer or a merchant; determining, by thecomputer-based system, an application criticality based on theapplication criticality score being above a pre-determined threshold;comparing, by the computer-based system, an operating system platform ofthe application processed by the server with the application criticalityof the application processed by the server; determining, by thecomputer-based system and based on the comparison, an end of life targetfor the server; determining, by the computer-based system, a designatedyear to replace the server, based on the end of life target;prioritizing, by the computer-based system, uplifts of each server ofthe plurality of servers to create a priority, wherein the prioritizingis based on a second set of technical and business parameters; andremoving, by the computer-based system, a server from the prioritizedlist of servers based on an indicator signifying the server ispreviously designated to be uplifted, wherein the indicator is retrievedfrom at least one of a server repository or an application repository.19. The method of claim 16, further comprising removing, by thecomputer-based system, a server from the prioritized list of serversbased on an indicator signifying the server is previously designated tobe uplifted out of turn and that a business unit is planning on payingfor the uplift.